chore: Bump Microsoft.EntityFrameworkCore.InMemory from 9.0.19 to 9.0.20 - #73
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
.NET
Merge assessment:
|
| Item | Status |
|---|---|
| Diff | 1 file, +1/−1 — Microsoft.EntityFrameworkCore.InMemory 9.0.19 → 9.0.20 |
| Checks | build-and-test ✅, submit-nuget ✅ |
Conflicts with main |
None |
The problem is the set, not this diff
Dependabot split the EF 9.0.20 bump into #71 (EntityFrameworkCore), #72 (Design) and #73 (this one), and opened none for Microsoft.EntityFrameworkCore.Relational, pinned at 9.0.19 under the comment:
Keep this on the same version as the other three EF entries.
#72 fails restore outright with NU1605 for precisely this reason. This PR passes because InMemory 9.0.20's floor on EntityFrameworkCore >= 9.0.20 is satisfied transitively in the test projects rather than tripping the downgrade check — so it resolves silently to a mixed 9.0.19/9.0.20 graph. Worth noting the blast radius is the EF InMemory provider, which is what the entire fast test tier (Odyssey.Core.Tests, Odyssey.Api.Tests, Odyssey.MigrationService.Tests) runs on, so a silent version skew there is skew under every fast suite.
Recommendation
Land all four EF entries in one change:
Microsoft.EntityFrameworkCore 9.0.20
Microsoft.EntityFrameworkCore.Design 9.0.20
Microsoft.EntityFrameworkCore.InMemory 9.0.20
Microsoft.EntityFrameworkCore.Relational 9.0.20
Verdict: safe content, unsafe in isolation. Hold.
Generated by Claude Code
|
Superseded by #80, which moves all four EF entries ( Close this once #80 is green. Generated by Claude Code |
adf741a to
383a790
Compare
--- updated-dependencies: - dependency-name: Microsoft.EntityFrameworkCore.InMemory dependency-version: 9.0.20 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
383a790 to
220788c
Compare
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Dependabot split this bump across three PRs (#71 EntityFrameworkCore, #72 Design, #73 InMemory) and opened none for Relational, so no combination of them restores a consistent set. #72 fails restore with NU1605: Design 9.0.20 floors Relational at 9.0.20 against the 9.0.19 pin. #71 and #73 pass only because their skew is not detectable, and merging either would leave a mixed 9.0.19/9.0.20 EF graph -- the exact state the Relational comment warns about. Moving all four entries together is what that comment asks for. Microsoft.AspNetCore.Identity.EntityFrameworkCore stays at 9.0.19: it sits on the same EF graph but has no 9.0.20 release, and 9.0.19 -> EF 9.0.20 is an upgrade direction, so it does not trip NU1605. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgQNXM18cyqjihnFrg3VoH
1 participant
Pinned Microsoft.EntityFrameworkCore.InMemory at 9.0.20.
Release notes
Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.
9.0.20
Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.19...v9.0.20
Commits viewable in compare view.